CVE-2015-8535

Summary of CVE-2015-8535: A directory traversal vulnerability in Lenovo Solution Center (LSC) prior to version 3.3.002 allows an attacker to execute arbitrary code with elevated privileges. Affected product: Lenovo Solution Center. Root cause: directory traversal enabling code execution via manip...

CVE-2015-8536

The connected CNVD entry for Lenovo Solution Center CSRF (CVE-2015-8536) confirms a cross-site request forgery vulnerability in Lenovo Solution Center versions before 3.3.002. Attackers could perform unauthorized operations via a malicious site or crafted URL, impacting integrity/availability of ...

CVE-2015-8534

This CVE (CVE-2015-8534) concerns Lenovo Solution Center (LSC). A local privilege escalation was fixed and publicly disclosed in 2015 for LSC versions prior to 3.3.002, enabling an unprivileged user to execute arbitrary code with elevated privileges. The issue is documented across multiple source...

CVE-2019-6177

CVE-2019-6177 affects Lenovo Solution Center version 03.12.003. A high-privilege Lenovo process overwrites the DACL of files in the C:\ProgramData\Lenovo\LSC\log\ directory, enabling a low-privileged user to create a hardlink to a target file and later have permissions elevated to write/modify th...

CVE-2016-5248

The CVE-2016-5248 issue affects Lenovo Solution Center versions older than 3.3.003. The StopProxy command in LSC.Services.SystemService allows local users to terminate arbitrary processes via the PID argument, indicating a local privilege/availability impact. Lenovo advisory LEN-7814 confirms the...

CVE-2016-1876

The CVE-2016-1876 issue concerns the Lenovo Solution Center backend service; prior to version 3.3.0002, a local user can escalate to SYSTEM privileges via unspecified vectors. Impact is Privilege Elevation on affected LS Center components, with the vulnerability described as local and high-severi...

CVE-2016-5249

Lenovo Solution Center (LSC) versions before 3.3.003 are affected by CVE-2016-5249, enabling local users to execute arbitrary code with LocalSystem privileges via the LSC.Services.SystemService StartProxy path using a pre-created named pipe and a crafted .NET assembly. The root cause involves a l...